Walkthrough

Updates composer.json’s phpstan script to include a memory limit flag, changing from "./vendor/bin/phpstan" to "./vendor/bin/phpstan --memory-limit=512M".

Changes

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• tests: increase PHP memory limit to 512M in Dockerfile #778 — Also addresses phpstan memory issues by setting PHP memory_limit to 512M in Docker, closely related to this script-level limit.

Suggested reviewers

• brunoocasali

Poem

A nibble of RAM for Stan to chew,
512M—now errors fewer and few.
I hop through scripts with whiskers bright,
Composer sings, the checks run right.
Tip-tap paws, CI in view—
Another leap, another review! 🐇✨

Pre-merge checks and finishing touches

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

What's the point of this?

I often run into memory issues when running composer phpstan locally.

This PR addresses the same memory limit issue fixed in #778. That other PR only focused on the Docker compose environment, though.

I can circumvent it by running ./vendor/bin/phpstan --memory-limit=512M instead, but I thought it would be better if the composer script contained the correct arguments.

What do you think?

But that depends on the environment. If i have much memory, why it should limit and run slower? 🙂

in #778 it was increased, so not the same

Thanks for the clarification! Indeed, everyone should configure it manually if needed